All Packages Class Hierarchy This Package Previous Next Index
There is a close relationship between Timeable objects and Taskable objects, A Timeable object's TimeBase will tick of its own accord - time marches on regardless. However Timeable objects generally have tasks that need to be performed at certain times. For instance, a movie needs to draw its next frame at time x, etc. Whilst some of the tasks that these objects perform are done at interrupt time, they also need to be given task time, time from the application when the tasks and schedules that they maintain can be performed outside of the constraints or system load of interrupt (or highest priority thread) time.
Thus these objects have a requirement to have some kind of task method called, in the case of a Movie it is MoviesTask, of a MovieController - MCIdle, a SpriteWorld - SpriteWorldIdle.
The tasking requirements of these classes maybe performed directly by the class itself (in the case of QTPlayer for example) or it maybe delegated to another class (as in the case of MoviePlayer).
public abstract TimeBase getTimeBase() throws QTException
public abstract void setRate(float rate) throws QTException
public abstract float getRate() throws QTException
All Packages Class Hierarchy This Package Previous Next Index